This file is intended to supplement the publications that you received with
the Concentrator.

  ****************************************************************************

                 More Information About the Concentrator
                 ---------------------------------------
 
  ************************************************************************
  *      *********       *********       *********       *********       *
  * **** IMPORTANT ***** IMPORTANT ***** IMPORTANT ***** IMPORTANT ****  *
  *      *********       *********       *********       *********       *
  ************************************************************************
  *                                                                      *
  *  When updating from V1.x to V2.10 or above level microcode, you must *
  *  load the diagnostic module (DGV#_#.BIN) before loading the other    *
  *  modules.                                                            *
  *                                                                      *
  *  WARNING: ONLY LOAD the DIAGNOSTICS code if the code on your 8230 is *
  *  WARNING: DOWN LEVEL.                                                *
  *  WARNING: IF THERE IS A FAILURE DURING THE DOWNLOAD OF DIAGNOSTICS,  *
  *  WARNING: THE FLASH MODULES CONTAINING THE DIAGNOSTICS MAY BE        *
  *  WARNING: DAMAGED CAUSING THE 8230 TO FAIL TO OPERATE UNTIL THE      *
  *  WARNING: MODULES ARE REPLACED. If this happens, contact your        *
  *  WARNING: IBM service representative and inform them that while      *
  *  WARNING: upgrading 8230 - 3/13 to version 2.1.0 or above the        *
  *  WARNING: diagnostics upload failed. FRU Part Number 25H5507 is      *
  *  WARNING: required to correct the problem.                           *
  *                                                                      *
  *  You may check the version of the diagnostics you currently have     *
  *  loaded by either of two methods.                                    *
  *                                                                      *
  *    1. The CCMF utility.                                              *
  *                                                                      *
  *          a. From the Main Menu i.e., at top of screen:               *
  *                                                                      *
  *          Main Menu - Concentrator Configuration/Management Facility  *
  *                                                                      *
  *             Select Load Operating Code by pressing <7> followed by   *
  *             <ENTER>.                                                 *
  *                                                                      *
  *          b. Select Code Level Information by pressing <3> followed   *
  *             by <ENTER>                                               *
  *                                                                      *
  *          c. Read the Diagnostics Microcode Level.                    *
  *                                                                      *
  *    2. Mib Browser.                                                   *
  *                                                                      *
  *          a. Read the mib variable 1.3.6.1.4.1.2.6.15.6               *
  *             (iso.org.dod.internet.private.enterprises.ibm.ibmprod.   *
  *              cauProdData.cauProdDataDiagCodeLevel) to obtain the     *
  *              Diagnostics Microcode Level.                            *
  *                                                                      *
  *  Following the instructions in your 8230 service guide               *
  *  load \DIAGS\DGVx_x.BIN from your 8230 Token-Ring Network            *
  *  Controlled Access Unit SNMP Support Diskette through the            *
  *  8230' rs232 port. Then you may load the other modules,              *
  *  in any order, as required.                                          *
  *                                                                      *
  *                                                                      *
  ************************************************************************

1.0 Notes on the Concentrator Configuration/Management Facility (CCMF)

    CCMF may indicate that a module is not installed during module
    initialization.  Refresh the module status after module initialization is
    complete to obtain the correct module status.  Initialization of the
    module may take up to 30 seconds.

    Any faults for lobes attached to the Concentrator are reported on
    the Modify Lobe and View Active Addresses panel as "Fault Detected"
    for the Fault Status parameter.

    When accessing CCMF using "Procomm for DOS" in a DOS session on OS/2,
    the following DOS settings should be set for that session:

        COM_HOLD          ON
        DOS_FILES         25
        IDLE_SECONDS      15
        IDLE_SENSITIVITY  100

    ****************************************************************************

2.0 Notes on configuring modems for use with CCMF

    Be sure to consult the documentation for your specific brand of modem.

    Be sure to read the information about modem configuration in the appendix
    titled "SNMP CCMF Overview" of the Installation and Service Guild.

    The modem attached to the device being used for CCMF should be
    configured so that the DCD signal tracks the state of the data carrier
    from the remote modem.  This is done with the &C1 command on most
    modems.

    If you wish to have the modem that is attached to the Concentrator
    disconnect, configure the way that the modem reacts to the Data Terminal
    Ready (DTR) signal.  This is done with the &D2 command on most modems.

    ****************************************************************************


3.0 Notes on managing the Concentrator with IBM AIX SystemView NetView/6000

    When using the MIB browser and/or the event display application of
    IBM AIX SystemView NetView/6000 with the concentrator, hexidecimal
    data is occasionally displayed as ASCII.  This happens when a MIB
    variable which is defined with the SNMP syntax "OctetString" has a
    first octet containing a value which is ASCII printable.  As an
    example, when the value of the cauDiagErrCode variable is 0x4031,
    the IBM AIX SystemView NetView/6000 MIB browser might display the value
    as the character string "@1".

    ****************************************************************************

4.0 Publication updates

    4.1 Updates to: 8230-003, 013, and 213 Model Controlled Access Unit
                    Installation and Service Guide SY27-0341-01

        1. Page 3-13 Correct the Yellow LED entry for the Fiber RI/RO to read
           "FLASH."
           NOTE: This change also applies to the '-02' version.
 
 
    4.2 Updates to: 8230-04A and 04P Model Controlled Access Unit
                    Installation and Service Guide SY27-0349-00


    4.3 Updates to: 8230-3 Model Controlled Access Unit
                    Service Guide SY27-0341-00

        1. Page 2-10 Added the following table immediately following Table
                     2.6

           Table 2.6A. Remote LAM LIU Control and Data LED States

           NOTE: Wait 60 seconds for conditions to stabilize and then see
                 the following table and take the appropriate actions.

           LEDs   |Control| Data |       Meaning       | Action Required
           -------|-------|------|---------------------|------------------------
           Green  |  ON   |  ON  | The Remote LAM and  | No action is required
                  |       |      | Remote LAM LIU are  |
           Yellow |  OFF  |  OFF | operating normally  |
           ---------------------------------------------------------------------
           Green  |  OFF  |  OFF | The Remote LAM LIU  | If there is no Remote
                  |       |      | is operating        | LAM connected to the
           Yellow |  OFF  |  OFF | normally but no     | Remote LAM LIU then no
                  |       |      | Remote LAM has been | action is required.
                  |       |      | detected since the  |
                  |       |      | the LIU has been    | If there is a Remote
                  |       |      | inserted into the   | LAM connected then
                  |       |      | 8230 or since the   | check the Remote
                  |       |      | last 8230 reset.    | LAM.
           ---------------------------------------------------------------------
           Green  |  ON   |  OFF | The Remote LAM LIU  | Check that the data
                  |       |      | is not communicating| connector is securely
           Yellow |  OFF  | BLINK| with the Remote LAM | seated.
                  |       |      | over the Data Link. |
                  |       |      |                     | Check the Remote LAM.
           ---------------------------------------------------------------------
           Green  | OFF   |  ON  | The Remote LAM LIU  | Check that the control
                  |       |      | is not communicating| connector is securely
           Yellow | BLINK |  OFF | with the Remote     | seated.
                  |       |      | LAM over the        |
                  |       |      | Control Link.       | Check the Remote LAM.
           ---------------------------------------------------------------------
           Green  | OFF   |  OFF | The Remote LAM LIU  | Check that the control
                  |       |      | has lost            | and data connectors
           Yellow | BLINK | BLINK| communication with  | are securely seated in
                  |       |      | the Remote LAM or   | the control and data
                  |       |      | has been disabled   | ports respectively.
                  |       |      | by the 8230.        |
                  |       |      |                     | Check the Remote LAM.
           ---------------------------------------------------------------------
           Green  | BLINK | BLINK| The Remote LAM LIU  | Contact the network
                  |       |      | has been disabled   | administrator.
           Yellow | OFF   | OFF  | by the network      |
                  |       |      | administrator.      |
                  |       |      |                     |
           ---------------------------------------------------------------------
           Green  | BLINK | BLINK| The Remote LAM LIU  | Contact the network
                  |       |      | has been disabled   | administrator.
           Yellow | BLINK | BLINK| by the network      |
                  |       |      | administrator and   |
                  |       |      | by the 8230.        |
           ---------------------------------------------------------------------
           Green  | OFF   | OFF  | The Remote LAM LIU  | Reseat the Remote LAM
                  |       |      | been disabled by    | LIU.
           Yellow | ON    | ON   | the 8230 because    |
                  |       |      | of a hardware error.| Wait 60 seconds for
                  |       |      |                     | conditions to
                  |       |      |                     | stabilize.
                  |       |      |                     |
                  |       |      |                     | If the condition
                  |       |      |                     | continues then replace
                  |       |      |                     | the Remote LAM LIU.
                  |       |      |                     |
                  |       |      |                     | If the condition
                  |       |      |                     | continues, contact your
                  |       |      |                     | next level of support.
           ---------------------------------------------------------------------
           Green  | LEDs in any  | A failure has       | Reseat the Remote LAM
                  | other state  | occurred in the     | LIU.
           Yellow |              | Remote LAM LIU      |
                  |              | or the 8230.        | Wait 60 seconds for
                  |              |                     | conditions to
                  |              |                     | stabilize.
                  |              |                     |
                  |              |                     | If the condition
                  |              |                     | continues, replace the
                  |              |                     | Remote LAM LIU.
                  |              |                     |
                  |              |                     | If the condition still
                  |              |                     | continues, contact your
                  |              |                     | next level of support.
           ---------------------------------------------------------------------

           NOTE: See the Remote Lobe Attachment Module Customer Setup
                 Instructions for procedures for debugging Remote LAM
                 related problems.



    2. Page 3-4  Add the following entry to the table:

                 Status or Error Code          Page

                 X'06 00'                      3-22
                 X'5n 00'                      3-26
                 X'5n 11'                      3-27
                 X'5n 80 - 5n 84'              3-27
                 X'5n 90'                      3-27
                 X'5n 91'                      3-27
                 X'5n A0 - 5n A1'              3-27
                 X'84 80 - 84 9F'              3-10
                 X'85 E1 - 85 E2'              3-8
                 X'86 0E'                      3-8
                 X'86 11 - 86 22'              3-8
                 X'86 31 - 86 42'              3-8
                 X'8M 00 - 8M 09'              3-8
                 X'CB 1E'                      3-13
                 X'CC xx'                      3-13
                 X'D0 15'                      3-16
                 X'EC 02'                      3-9
                 X'EC 03'                      3-9
                 X'EC 81                       3-9
                 X'EC 82                       3-9
                 X'EC 83'                      3-9
                 X'F4 00 - F4 10'              3-8
                 X'F4 E0 - F4 E2'              3-8
                 X'F4 F1 - F4 FF'              3-8
                 X'F6 01'                      3-17
                 X'F8 01 - F8 0B'              3-17
                 X'F8 B0'                      3-17

                 ***************************************************************
                 ** NOTE: CHECK THE TEXT BELOW FOR THE APPROPRIATE PROCEDURES **
                 **       FOR THE ABOVE ERROR CODES.                          **
                 ***************************************************************


    6. Page 3-8 Add the following new error codes.

                 ---------------------------------------------------------------
                 | X'85 E1 - 85 E2'  Expected interrupt not received           |
                 | X'86 0E'          RS232 Hardware Problem Detected           |
                 | X'86 11 - 86 22'  RS232 Hardware Problem Detected           |
                 | X'86 31 - 86 42'  RS232 Hardware Problem Detected           |
                 | X'F4 E0 - F4 E2' An expected interrupt did not occur        |
                 | X'F4 F1 - F4 FF' An unexpected interrupt occurred           |
                 ---------------------------------------------------------------

                 Cause: The Model 3 displays this error when there is a
                 problem with the 8230 processor board.

                 Action: Perform the following actions

                   1. Reset the Model 3 by turning the power off,
                      waiting 20 seconds, turning the power back on,
                      and waiting approximately 60 seconds for the
                      model 3 to complete its diagnostics.

                   2. If the error code continues to be displayed,
                      replace the Processor Board.

                   3. If the error code does not reappear, test the
                      Model 3 to verify the repair.

                   4. If the error code continues to be displayed,
                      contact your next level of support.
    7. Page 3-8 Add the following new error codes.

                 ---------------------------------------------------------------
                 | X'8M 00 - 8M 09'  The 8230 is in manufacturing mode.        |
                 ---------------------------------------------------------------

                 Cause: Pins 9 and 10 of the 8230 port are shorted together.

                 Action: Perform the following actions

                 1. Check to see if the cable connected to the 8230's RS/232
                    port has pins 9 and 10 shorted together. If this is the
                    case then replace the cable.

                 2. Reset the Model 3 by turning the power off,
                    waiting 20 seconds, turning the power back on,
                    and waiting approximately 60 seconds for the
                    model 3 to complete its diagnostics.

                 3. If the error code continues to be displayed,
                    replace the Processor Board.

                 4. If the error code does not reappear, test the
                    Model 3 to verify the repair.

                 5. If the error code continues to be displayed,
                    contact your next level of support.

    8. Page 3-8 Add the following new error codes.

                 ---------------------------------------------------------------
                 | X'F4 00 - F4 10' Problem detected with the 8230's internal  |
                 |                  Token Ring hardware                        |
                 ---------------------------------------------------------------
                 Cause: The Model 3 displays this error when there is a
                 problem with the 8230 internal Token Ring Hardware.

                 Action: Perform the following actions

                   1. Reset the Model 3 by turning the power off,
                      waiting 20 seconds, turning the power back on,
                      and waiting approximately 60 seconds for the
                      model 3 to complete its diagnostics.

                   2. If the error code continues to be displayed,
                      and the error code is X'F4 02', X'F4 04', or
                      X'F4 0C' then replace the Dual Ring Redundancy
                      Feature.

                   3. If the error code does not reappear, test the
                      Model 3 to verify the repair.

                   4. If the error code continues to be displayed,
                      replace the Processor Board.

                   5. If the error code does not reappear, test the
                      Model 3 to verify the repair.

                   6. If the error code continues to be displayed,
                      contact your next level of support.

    3. Page 3-9  Change the error code which reads:
                 -------------------------------------------------------
                 | X'EC 01'  RAM Parity Error                          |
                 -------------------------------------------------------

                 to read:

                 -------------------------------------------------------
                 | X'EC 01', X'EC 81' RAM Parity Error                 |
                 | X'EC 02', X'EC 82' I/O Check error                  |
                 -------------------------------------------------------

                 The cause and actions remain the same.

    4. Page 3-9  Add the following error codes:
                 -------------------------------------------------------
                 | X'EC 03', X'EC 83' Deadman Timeout                  |
                 -------------------------------------------------------
                 Cause: The Model 3 displays this error when there is a
                 problem with the 8230 software or the processor
                 board.

                 Action: Perform the following actions

                   1. Reset the Model 3 by turning the power off,
                      waiting 20 seconds, turning the power back on,
                      and waiting approximately 60 seconds for the
                      model 3 to complete its diagnostics.

                   2. If the error code continues to be displayed,
                      replace the Processor Board.

                   3. If the error code does not reappear, test the
                      Model 3 to verify the repair.

                   4. If the error code continues to be displayed,
                      contact your next level of support.

    5. Page 3-10 Change the error code which reads:
                 ---------------------------------------------------------------
                 | X'A1 01 - A1 06'                                            |
                 | X'A1 08 - A1 0E' FLASH Code or Memory Errors as follows     |
                 | X'A1 01'     Checksum Error--Main Operational Code          |
                 | X'A1 02'     Checksum Error--Remote Program Load (RPL) Code |
                 | X'A1 03'     Checksum Error--Main Operational Code and RPL  |
                 |                              Code                           |
                 | X'A1 04'     Checksum Error--RS232 Load Code (This code     |
                 |                              implements CCMF.)              |
                 | X'A1 05'     Checksum Error--Main Operational Code and RS232|
                 |                              Load Code                      |
                 | X'A1 06'     Checksum Error--RPL Code and RS232 Load Code   |
                 | X'A1 08'     Checksum Error--Bring-Up Diagnostic Code       |
                 | X'A1 09'     Checksum Error--Main Operational Code and      |
                 |                              Bring-Up Diagnostic Code       |
                 | X'A1 0A'     Checksum Error--RPL Code and Bring-Up          |
                 |                              Diagnostic Code                |
                 | X'A1 0B'     Checksum Error--Main Operational Code, RPL     |
                 |                              Code and Bring-Up Diagnostic   |
                 |                              Code                           |
                 |                                                             |
                 | X'A1 0C'     Checksum Error--RS232 Code and Bring-Up        |
                 |                              Disgnostic Code.               |
                 | X'A1 0D'     Checksum Error--Main Operational Code, RS232   |
                 |                              Code, and Bring-Up Diagnostic  |
                 |                              Code.                          |
                 | X'A1 0E'     Checksum Error--RPL Code, RS232 Load Code, and |
                 |                              Bring-Up Diagnostic Code       |
                 ---------------------------------------------------------------
                 Cause: The Model 3 displays one of these error codes when it
                 has detected an error on the microcode while running internal
                 diagnostics.

                 Action: Perform the following actions:

                 1. Try to reload the microcode, if possible. Before you try to
                    reload the microcode, verify that the file is correct. See
                    Appendix C, "Uploading Code or Restarting the Model 3" if
                    you need instructions for uploading code.

                    These codes may reflect a problem with the RS232 Load Code,
                    the RPL Code, both of these, or neither of them.

                 2. The following codes reflect a problem with the RS232 Load
                    Code: 04, 05, 0C, and 0D. For these codes, try to upload
                    a replacement for the microcode using the SNMP manager,
                    such as IBM SystemView NetView/6000, with Trivial File
                    Transfer Protocol(TFTP). If you are not using an SNMP
                    manager, go to step 6.

                 3. The following codes reflect a problem with the RPL Code: 02,
                    03, 0A, and 0B. For these errors, try to upload a replacement
                    for the microcode using CCMF through the EIA 232 Port.

                 4. These three codes reflect problems with neither the RS232
                    Code nor the RPL Code: 01, 08, and 09. Use either CCMF
                    or the SNMP network manager (TFTP) to try to upload the
                    replacement microcode.

                 5. These two codes reflect a problem with both the RS232
                    Code and the RPL Code: 06 and 0E. For these codes, do
                    not try to upload the microcode.
                    Continue with step 6.

                 6. If the error code continues to be displayed, replace the
                    Processor Board.

                 7. If the error code does not reappear, test the Model 3.

                 8. If the error code continues to be displayed, contact
                    your next level of support.

                 to read:
                 ---------------------------------------------------------------
                 | X'84 80 - 84 9F'                                            |
                 | X'A1 01 - A1 06'                                            |
                 | X'A1 08 - A1 0E' FLASH Code or Memory Errors as follows     |
                 |                                                             |
                 | X'84 80', X'84 84', X'84 88' Flash Error--Main Operational  |
                 |                                           Code              |
                 | X'84 81', X'84 85', X'84 89' Flash Error--Remote Program    |
                 |                                           Load (RPL) Code   |
                 | X'84 82', X'84 86', X'84 8A' Flash Error--RS232 Load Code   |
                 |                                           (This Code        |
                 |                                            implements CCMF) |
                 | X'84 83', X'84 87', X'84 8B' Flash Error--Bring-Up          |
                 |                                           Diagnostic Code   |
                 | X'84 90', X'84 94', X'84 98' Flash Error--Main Operational  |
                 |                                           Code              |
                 |                                           and unexpected    |
                 |                                           error             |
                 |                                           detected in       |
                 |                                           Bring-Up          |
                 |                                           Diagnostic Code.  |
                 | X'84 91', X'84 95', X'84 99' Flash Error--Remote Program    |
                 |                                           Load Code         |
                 |                                           and unexpected    |
                 |                                           error             |
                 |                                           detected in       |
                 |                                           Bring-Up          |
                 |                                           Diagnostic Code.  |
                 | X'84 92', X'84 96', X'84 9A' Flash Error--RS232 Load Code   |
                 |                                           and unexpected    |
                 |                                           error             |
                 |                                           detected in       |
                 |                                           Bring-Up          |
                 |                                           Diagnostic Code.  |
                 | X'84 93', X'84 97', X'84 9B' Flash Error--Bring-Up          |
                 |                                           Diagnostic Code   |
                 |                                           and unexpected    |
                 |                                           error             |
                 |                                           detected in       |
                 |                                           Bring-Up          |
                 |                                           Diagnostic Code.  |
                 |                                                             |
                 | X'A1 01', X'84 8C' Checksum Error--Main Operational Code    |
                 | X'84 9C'           Checksum Error--Main Operational Code    |
                 |                                    and unexpected error     |
                 |                                    detected in Bring-Up     |
                 |                                    Diagnostic Code.         |
                 | X'A1 02', X'84 8D' Checksum Error--Remote Program Load      |
                 |                                    Code                     |
                 | X'84 9D'           Checksum Error--Remote Program Load      |
                 |                                    Code and unexpected      |
                 |                                    error detected in        |
                 |                                    Bring-Up Diagnostic      |
                 |                                    Code.                    |
                 | X'A1 03'           Checksum Error--Main Operational Code    |
                 |                                    and RPL Code             |
                 | X'84 9E'           Checksum Error--RS232 Load Code and      |
                 |                                    unexpected error         |
                 |                                    detected in Bring-Up     |
                 |                                    Diagnostic Code.         |
                 | X'94 9F'           Checksum Error--Bring-Up Diagnostic Code |
                 |                                    and unexpected error     |
                 |                                    detected in Bring-Up     |
                 |                                    Diagnostic Code.         |
                 | X'A1 04',          Checksum Error--RS232 Load Code          |
                 | X'89 E0'           Checksum Error--Main Operational Code,   |
                 |                                    RPL Code, and RS232 Load |
                 |                                    Code.                    |
                 | X'89 E1', X'8A EC'          Error--Unexpected error         |
                 |                                    detected in Bring-Up     |
                 |                                    Diagnostic Code.         |
                 | X'A1 9F', X'84 8E' Checksum Error--RS232 Load Code          |
                 |                                                             |
                 | X'A1 05'           Checksum Error--Main Operational Code    |
                 |                                    and RS232 Load Code      |
                 | X'A1 06'           Checksum Error--RPL Code and RS232 Load  |
                 |                                    Code                     |
                 | X'A1 08', X'84 8F' Checksum Error--Bring-Up Diagnostic Code |
                 | X'A1 09'           Checksum Error--Main Operational Code    |
                 |                                    and Bring-Up Diagnostic  |
                 |                                    Code                     |
                 | X'A1 0A'           Checksum Error--RPL Code and Bring-Up    |
                 |                                    Diagnostic Code          |
                 | X'A1 0B'           Checksum Error--Main Operational Code,   |
                 |                                    RPL Code and Bring-Up    |
                 |                                    Diagnostic Code          |
                 |                                                             |
                 | X'A1 0C'           Checksum Error--RS232 Code and Bring-Up  |
                 |                                    Disgnostic Code.         |
                 | X'A1 0D'           Checksum Error--Main Operational Code,   |
                 |                                    RS232 Code, and Bring-Up |
                 |                                    Diagnostic Code.         |
                 | X'A1 0E'           Checksum Error--RPL Code, RS232 Load     |
                 |                                    Code, and Bring-Up       |
                 |                                    Diagnostic Code          |
                 ---------------------------------------------------------------
                 Cause: The Model 3 displays one of these error codes when it
                 has detected an error on the microcode while running internal
                 diagnostics.

                 Action: Perform the following actions:
                 1. Try to reload the microcode, if possible. Before you try to
                    reload the microcode, verify that the file is correct. See
                    Appendix C, "Uploading Code or Restarting the Model 3" if
                    you need instructions for uploading code.

                    These codes may reflect a problem with the RS232 Load Code,
                    the RPL Code, both of these, or neither of them.

                 2. The following codes reflect a problem with the RS232 Load
                    Code: 8482, 8486, 848A, 848E, 8492, 8496, 849A, 849E, A104,
                    A105, A10C, A10D, and A19F. For these codes, try to upload a
                    replacement for the microcode using the SNMP manager, such
                    as IBM SystemView NetView/6000, with Trivial File Transfer
                    Protocol(TFTP). If you are not using an SNMP manager, go to
                    step 6.

                    NOTE: For the error codes also reflecting diagnostics
                    problems (i.e., 8492, 8496, 849A, 849E, A10C, and A10D),
                    load the diagnostics code before other code modules .

                 3. The following codes reflect a problem with the RPL Code:
                    8481, 8485, 8489, 848D, 8491, 8495, 8499, 849D, A102, A103,
                    A10A, and A10B. For these errors, try to upload a
                    replacement for the microcode using CCMF through the
                    EIA 232 Port.

                    NOTE: For the error codes also reflecting diagnostics
                    problems (i.e.,8491, 8495, 8499, 849D, A10A, and A10B),
                    load the diagnostics code before other code modules.

                 4. These three codes reflect problems with neither the RS232
                    Code nor the RPL Code: 8480, 8483, 8484, 8487, 8488, 848B,
                    848C, 848F, 8490, 8493, 8494, 8497, 849B, 849C, 89E1, 8AEC,
                    9498, 949F, A101, A108, and A109. Use either CCMF or the
                    SNMP network manager (TFTP) to try to upload the replacement
                    microcode.

                    NOTE: For the error codes also reflecting diagnostics
                    problems (i.e., 8483, 8487, 848B, 848F, 8490, 8493, 8494,
                    8497, 849B, 849C, 89E1, 8AEC, 9498, 949F, A108, and A109),
                    load the diagnostics code before other code modules.

                 5. These codes reflect a problem with both the RS232
                    Code and the RPL Code: 89E0, A106, A10E. For these codes,
                    do not try to upload the microcode. Contact your IBM service
                    representative and inform him/her that you require the
                    installation of FRU Part Number 13H6744 to correct your
                    problem. When the FRU is installed, continue with step 6.

                 6. If the error code continues to be displayed, replace the
                    Processor Board.

                 7. If the error code does not reappear, test the Model 3.

                 8. If the error code continues to be displayed, contact
                    your next level of support.


    9. Page 3-13 Add the following new error code. X'CB 1E'

                 Change the error code block which reads:

                 ---------------------------------------------------------
                 | X'CB 1C-CB 1D' CCMF Program Error                     |
                 ---------------------------------------------------------

                 to read:

                 ---------------------------------------------------------
                 | X'CB 1C-CB 1E' CCMF Program Error                     |
                 ---------------------------------------------------------

    10. Page 3-13 Change the error code block which reads:

                 ---------------------------------------------------------
                 | X'CC Cx' TFTP Processor Program Error                 |
                 ---------------------------------------------------------

                 to read:

                 ---------------------------------------------------------
                 | X'CC xx' TFTP Processor Program Error                 |
                 ---------------------------------------------------------

    11. Page 3-16 Add the following new error code:

                 -------------------------------------------------------
                 | X'D0 15' Slot 1 Configuration Change                |
                 -------------------------------------------------------

                 Cause: A non RI/RO LIU module was replaced by
                 a RI/RO LIU module.

                 Action: The Model 3 will automatically reboot.
                 After the reboot, the X'D015' code is displayed
                 for approximately 10 seconds. Then, the code is
                 no longer displayed and the model 3 should resume
                 normal operation.

                 No action required

    12. Page 3-17 Add the following new error code:

                 -------------------------------------------------------
                 | X'F6 01' Unable to Isolate Ring Error               |
                 -------------------------------------------------------

                 Cause: This error code is displayed when the Model 3
                 is unable to isolate a ring error condition.

                 Action: Perform the following actions.

                 1.) Check Token Ring cables and connections and stations.

                 2.) Contact your IBM service representative.

    13. Page 3-17 Add the following new error codes. X'F8 01 - F8 0B', X'F8 B0'

                 Change the error code block which reads:

                 ---------------------------------------------------------
                 | X'F8 1x-F8 3x' Program Error                          |
                 | X'F8 Ax'                                              |
                 | X'F8 B0'                                              |
                 | X'F8 B1-F8 B3'                                        |
                 | X'F8 BA-F8 BF'                                        |
                 | X'F8 FF'                                              |
                 ---------------------------------------------------------

                 to read:

                 ---------------------------------------------------------
                 | X'F8 01-F8 0B' Program Error                          |
                 | X'F8 1x-F8 3x'                                        |
                 | X'F8 Ax'                                              |
                 | X'F8 B1-F8 B3'                                        |
                 | X'F8 BA-F8 BF'                                        |
                 | X'F8 FF'                                              |
                 ---------------------------------------------------------

    13. Page 3-22 Add the following new error code. X'06 00'

                 Change the error code block which reads:

                 ---------------------------------------------------------
                 | X'05 00' Congestion causing Buffer Overflow           |
                 ---------------------------------------------------------

                 to read:

                 ---------------------------------------------------------
                 | X'05 00', X'06 00' Congestion causing Buffer Overflow |
                 | X'05 01', X'05 02'                                    |
                 ---------------------------------------------------------

    14. Page 3-26 Add the following new error code. X'5n 00'

                 Change the error code block which reads:

                 ---------------------------------------------------------
                 | X'5n 01-5n 05' LIU Hardware Error, n=1 to 5           |
                 | X'5n 07'                                              |
                 | X'5n 0A-5n 0C'                                        |
                 | X'5n 0F'                                              |
                 ---------------------------------------------------------

                 to read:

                 ---------------------------------------------------------
                 | X'5n 00-5n 05' LIU Hardware Error, n=1 to 5           |
                 | X'5n 07'                                              |
                 | X'5n 0A-5n 0C'                                        |
                 | X'5n 0F'                                              |
                 ---------------------------------------------------------




    15. Page 3-27 Add the following new error code:

                 -------------------------------------------------------
                 | X'5n 11' LIU Read Error, n=1 to 5                   |
                 -------------------------------------------------------
                 Cause: The Model 3 displays one of these error codes
                 when an LIU read error is detected.

                 Action: Perform the following actions.

                  1.) If the error occurs while hot-plugging module n,
                      the error is normal so ignore it.

                  2.) If it happens during normal operation, replace
                      the LIU in slot number n.

    16. Page 3-27 Add the following new error codes:

                 ------------------------------------------------------------
                 | X'5n 80 - 5n 84' Remote LAM LIU Hardware Error, n=1 to 5 |
                 ------------------------------------------------------------

                 Cause: The 8230 displays one of these error codes when the
                 Remote LAM LIU diagnostics detects a hardware malfunction
                 with the indicated Remote LAM LIU.

                 Action: Perform the following actions.

                 1. If the yellow Remote LAM LIU LEDs remain lit for more than
                    60 seconds, replace the indicated Remote LAM LIU.

                 2. If the error code continues to be displayed, contact
                    your next level of support.


                 ------------------------------------------------------------
                 | X'5n 90' Remote LAM LIU Control Link down, n=1 to 5      |
                 ------------------------------------------------------------

                 Cause: The 8230 displays one of these error codes when the
                 control link is down between the indicated Remote LAM LIU
                 and the Remote LAM Control Ports.

                 Action: Perform the following actions.

                 1. Check that the control cable is connected to both the
                    Remote LAM LIU and the Remote LAM control ports,

                 2. Check the Remote LAM. Follow the error maps beginning in
                    chapter 4 of the Remote Lobe Attachment Module Customer
                    Setup Instructions (GA27-4987-00).


                 --------------------------------------------------------------
                 | X'5n 91' Remote LAM LIU Data Cable Not Detected, n=1 to 5  |
                 --------------------------------------------------------------

                 Cause: The 8230 displays one of these error codes when the
                 data cable is not detected between the Remote LAM LIU and
                 the Remote LAM data ports.

                 Action: Perform the following actions.

                 1. Check that the data cable is connected to both the
                    Remote LAM LIU and the Remote LAM data ports,

                 2. Check the Remote LAM. Follow the error maps beginning in
                    chapter 4 of the Remote Lobe Attachment Module Customer
                    Setup Instructions (GA27-4987-00).


                 --------------------------------------------------------------
                 | X'5n A0 - 5n A1' Remote LAM Hardware Error, connected to   |
                 |                  Remote LAM LIU n, n=1 to 5                |
                 --------------------------------------------------------------

                 Cause: The 8230 displays one of these error codes when the
                 8230 detects a diagnostics error on the Remote LAM.

                 Action: Perform the following actions.

                 1. Check the Remote LAM. Follow the error maps beginning in
                    chapter 4 of the Remote Lobe Attachment Module Customer
                    Setup Instructions (GA27-4987-00).



    ****************************************************************************


    4.1 Updates to: 8230-3 Model Controlled Access Unit
                Customer Setup Instructions GA27-4061-00


        1. Page 3-13 Replace Table 3-3 with the new Table 3 below:


                 Table 3-3 RI/RO LEDS Status after Diagnostics
                 ________________________________________________
                 RI/RO Port Type   Wrap LED  Green LED Yellow LED
                 ________________________________________________
                 ICS                 OFF       ON         OFF
                 ________________________________________________
                 Fiber               ON        OFF        OFF
                 ________________________________________________
                 RJ-45               ON        OFF        FLASH


        2. Add a new section "D" in Chapter 3 on page 3.13 just before
           step 5:



           D   Remote LAM LIU LEDs after diagnostics

           LEDs   |Control| Data |       Meaning       | Action Required
           -------|-------|------|---------------------|------------------------
           Green  |  OFF  |  OFF | The Remote LAM LIU  | If there is no Remote
                  |       |      | is operating        | LAM connected to the
           Yellow |  OFF  |  OFF | normally but no     | Remote LAM LIU then no
                  |       |      | Remote LAM has been | action is required.
                  |       |      | detected since the  |
                  |       |      | the LIU has been    | If there is a Remote
                  |       |      | inserted into the   | LAM connected then
                  |       |      | 8230 or since the   | check the Remote
                  |       |      | last 8230 reset.    | LAM.


           All of the LEDs should be off unless the 8230 has previously been
           configured by the network manager. If the green LEDs are blinking,
           then the module has been disabled by the network manager, Contact
           the network administrator to enable this module.


        3. Page 5-8 Replace the note at the bottom of page 5-8 which
                    reads:

                    Note: This function cannot be enabled if the Passive
                    Concentrator Attachment Privileges parameter is
                    enabled on this lobe.

                    With the new note below:

                    Note: This function cannot be enabled on a lobe if
                    the Passive Concentrator Attachment Privileges (PCAP)
                    function is already active on the same lobe. Also, if
                    PCAP is enabled on a lobe with SVF already enabled, SVF
                    will automatically be disabled.


        4. Page 5-9 Replace the note under the heading "Passive
                    Concentrator Attachment Privileges" which reads:

                    Note: If SVF is enabled on the lobe, PACP cannot be
                    enabled.

                    With the new note below:

                    Note: If PACP is enabled on a lobe with SVF already
                    enabled, SVF will be automatically disabled.



        5. Page 4-13 Add the following as a new step before step 5
           and renumber steps 5 and 6 to steps 6 and 7 respectively.

           5. Cable the Remote LAM LIUs.

              * Connect the other end of the control and data cables
                connected to the appropriate Remote LAM to the control
                and data ports of the Remote LAM LIU respectively.

                If patch cables are used, ensure they are rated at least
                as good as the lobe wiring.

              * Route the cables out through the right end of the
                cable bracket until you cable the LIU in slot 3. Then, route
                the cables out through the left end of the cable bracket.



        6. Add the following to the tables on page 5-7

                                                            Maximum Number of
                                                            Remote LAMS
           Type               Type Definition               supported
           ---------------------------------------------------------------------
           Remote LAM LIU     RJ-45 connectors; supports    1
                              attachment of Remote LAM
                              up to 100 m (328 ft) away
           ---------------------------------------------------------------------

                                                            Maximum Number of
                                                            Remote LAMS
           Type               Type Definition               supported
           ---------------------------------------------------------------------
           Active Remote      RJ-45 connectors;             16
           LAM                See Chapter 2 in the
                              Remote Lobe Attachment
                              Module Customer Setup
                              Instructions (GA27-4987-00)
                              for the appropriate drive
                              distance information.
           ---------------------------------------------------------------------
           Passive Remote     RJ-45 connectors; supports    16
           LAM                signal up to 100 m (328 ft)
                              up to 100 m (328 ft)
           ---------------------------------------------------------------------


        7. Add the following note at the very end the section on the
           Speed Verification Function on page 5-8.

           Note: If a wrong speed station attached to an Active Remote LAM
           attempts to enter the ring its Lobe Media Test will normally fail
           and the adapter will terminate its open process without entering
           the ring. This occurs whether or not the Speed Verification
           Function is enabled on the appropriate port.
           If an adapter fails to terminate its open process and
           actually attempts to enter the ring and SVF in enabled on its
           port of a Active RLAM, the wrong speed adapter will be
           detected and prevented from entering the ring.


        8. Page 5-9 Add the following sentence to the paragraph under
                    Passive Concentrator Attachment Privileges:

                    PACF is not currently supported on RJ45 LIUs or on RLAMs.

    ****************************************************************************


    4.4 Updates to: Remote Lobe Attachment Module
                    Customer Setup Instructions GA27-4987-00


        1. Page 1-5 Add the following note after section "E Port LEDs":

           NOTE: If all of the port LEDs on the Remote LAM
                 continue to flash for more than 60 seconds, suspect
                 that the Remote LAM has lost communication with the
                 8230. Follow the error maps in Chapter 4 to
                 isolate the problem.


        2. Page 5-2 Add the following entries to the end of the
           Index to Remote LAM and LIU Status and Error Codes.


          Status or Error Code     Page

          X'5n80' - X'5n84         5-4
          X'5n90'                  5-4
          X'5n91'                  5-4
          X'5nA0' - X'5nA1         5-5


        3. Page 1-3 Replace the section "Wrong Speed Blocking" with the
           following:


           Handling of Wrong Speed Stations

           The Speed Verification Function (SVF) prevents interruptions to
           the network when a token ring adapter attempts to enter the
           ring when it is configured at the wrong speed. It also prevents
           other devices, such as a monochrome adapter from disrupting
           the ring.

           If a wrong speed station attached to an Active RLAM attempts to
           enter the ring its Lobe Media Test will normally fail and the
           adapter will terminate its open process without entering the
           ring. This occurs whether or not the Speed Verification
           Function is enabled on the appropriate port.

           If an adapter fails to terminate its open process and
           actually attempts to enter the ring and SVF in enabled on its
           port of a Active RLAM, the wrong speed adapter will be
           detected and prevented from entering the ring. If the
           8230 has been so configured, the network manager is
           notified that a wrong speed adapter attempted to enter the ring.

           If SVF in enabled on a port of a Passive RLAM, the wrong speed
           adapter is detected and prevented from entering the ring. If the
           8230 is so configured, the network manager is
           notified that a wrong speed adapter attempted to enter the ring.


        4. Page 5-4 Add a new step under the action list for:

                 --------------------------------------------------------------
                 | X'5n 91' Remote LAM LIU Data Cable Not Detected, n=1 to 5  |
                 --------------------------------------------------------------

           The following new step should be added after step 2
           and renumber steps 3 and 4 to steps 4 and 5 respectively.

                 3. If the error code continues to be displayed and the
                    control cable appears to be connected, then the control
                    cable may be defective; replace the control cable,

    4.5 Updates To: 8230 Models 003, 013, and 213 Token-Ring Network
                    Controlled Access Unit Installation and Service Guide SY27-0341-01.

        1.          Additions For RMON - See Section 8.0 below


5.0 Network Management Notes

        1. PTF U434441 for version 1.0 of LNM for AIX is required to
           enable LNM to manage an 8230 with the level of code supplied
           on this diskette.


        2. 8230 Device Management for Windows** PTF, Version 1.01
           (PTF # UR43376) or greater is required to allow for
           the management of an 8230 with Remote LAM LIUs
           installed.

           This PTF allows management of a Remote LAM through the
           mib browser only.


        ** Trademark of Microsoft Corporation.

    ****************************************************************************

6.0 Changing to SNMP Network Management Mode from CMOL Network Management Mode

    For 8230 Mod 3/xx3, to update the 8230 microcode from CMOL to SNMP management,
    perform the following steps, in order:

      NOTE: Keep the SNMP/CMOL switch to the CMOL position until you are
            instructed to switch it to SNMP.

      Step 1: Determining the 8230 Microcode Level

         - Verify the microcode levels of your 8230 and record them for
           future use.
         - Continue with Step 2.

      Step 2: Update the 8230 Diagnostic Microcode if necessary

         - If the diagnostics microcode level of your 8230 is at version 2.1.0
           or higher, go to step 3.

         - Upload DGV4_1.bin from the SNMP Support Diskette directly through
           the EIA 232 port.

         - After loading the diagnostic microcode, select "No" to the question
           "Do you want to load more files?". This will automatically restart
           the 8230.

           Note: If there is a failure during the upload of the diagnostics,
           the FLASH modules containing the diagnostics can be damaged.  This
           will cause the 8230 to fail to operate until the FLASH
           modules are replaced.

           If the 8230 fails, contact your service representatives and inform
           them that during the upgrade of the 8230 diagnostics to Version
           4.1.0, the upload failed. FRU part number 25H5507 is required to
           correct the problem.

           Verify microcode level update. The diagnostic microcode level of
           your 8230 should now be at Version 4.1.0.

           Continue with step3.

      Step 3: Updating the EIA 232 Code Load Microcode

         - If the EIA 232 upload microcode level of your 8230 is at Version
           4.1.0 or higher, go to step 4.

         - Upload R232V5_3.bin from the SNMP Support Diskette directly through
           the EIA 232 port.

         - After loading the EIA 232 Upload microcode, select "No" to the
           question "Do you want to load more files?".  This will
           automatically restart the 8230.

         - Verify the microcode level update. The EIA 232 upload microcode
           level of your 8230 should now be Version 5.3.0.

         - Continue to step 4.

      Step 4: Update the SNMP Operational and RPL Code Load

         - Upload OPV5_3.bin from the SNMP Support Diskette directly through
           the EIA 232 port.

         - After loading the OPV5_3.bin file, select "Yes" when asked if you
           want to load more files.

         - Upload RPLV5_3.bin from the SNMP Support Diskette directly through
           the EIA 232 port.

         - Set the SNMP/CMOL switch in the SNMP position only only after
           uploading RPLV5_3.bin.

         - Select "No" to the question "Do you want to load more files?".
           This will automatically restart the 8230.

         - CMOL to SNMP management update is now complete.

7.0 Known RMON deviations

    - If the ringStationStatus should be forcedRemoval (3) the 8230 will report
      the ringStationStatus as inactive (2).

      The ringStationStatus should be forcedRemoval when the reason the mac 
      adapter took itself off of the ring was that it received 
      a Remove Ring Station mac frame. One way to cause such a frame to be
      sent is by setting the RMON ringStationConfigControlRemove variable
      to removing (2) for the mac the manager desires to be removed.


     - NOTE: The following only apply on 8230's with PRE NM05A60 level
             mac code (see cauProdDataMACcodeLevel via SNMP). If desired, 
             a MAC EPROM upgrade kit (FRU PN 25H5508) can be purchased
             through your IBM service representative.

             - tokenRingMLStatsRingPurgePkts and tokenRingMLStatsClaimTokenPkts
               counts may be low. If there is an uninterrupted burst of
               identical Ring Purge or Claim Token packets, only the first one
               in the sequence will be counted.

               - If the above occurs, this will cause tokenRingMLStatsMacPkts
                 and tokenRingMLStatsMacOctets to be correspondingly low.

8.0 Updates To: 8230 Models 003, 013, and 213 Token-Ring Network
                Controlled Access Unit Installation and Service Guide.


    1. Add the following section to the top of page 1-6.

    Remote Network Monitoring Management Information Base
    -----------------------------------------------------

    The 8230 model 3/13 and 213 supports the following Remote Network
    Monitoring Management Information Base (RMON) groups as described in
     rfc1271 - Remote Network Monitoring Management Information Base and
     rfc1513 - Token Ring Extensions to the Remote Network Monitoring MIB:
    
         - The Token Ring Mac-Layer Statistics Group
    
             The Token Ring Mac-Layer Statistics Group collects information,
             including error reports, from Mac Layer frames on the local ring. 
    
         - The Token Ring Ring Station Group
    
             The Token Ring Ring Station Group contains statistics and status
             information associated with each Token Ring station on the local
             ring.  
    
         - The Token Ring Ring Station Order Group
    
             The Token Ring Ring Station Order Group provides the order of the
             stations on the ring.
    
         - The Token Ring Ring Station Config Group
    
             The Token Ring Ring Station Config Group manages token ring stations
             through active means. Stations on the ring may be removed
             or have configuration information downloaded from them.
    

    2. Delete the description of the X'D0 15' code at the bottom of page 7-18.
       The correct description is on page 7-20.
 
 
    3. Add Appendix L. Initiating and Stopping Data Collection On RMON Tables

    The following instructions initiate and stop data collection for the 
    various RMON tables that the 8230 models 003, 013, and 213 support. 
    Following is a quick list of the specifics for the RMON groups supported 
    by the 8230 models 003, 013, and 213.

    This is followed by a generic description which explains in general how
    EntryStatus variables are used to conrtol the starting and stopping of
    data collection on an RMON probe.

    Legend for the following section:
 
        valid         = 1
        createRequest = 2
        underCreation = 3
        invalid       = 4
 
        stable        = 1
        updating      = 2
 
   - The Token Ring Mac-Layer Statistics Group
 
     To invalidate the table:
 
        - set tokenRingMLStatsStatus = invalid
 
     To initiate data collection on the table :
 
        - set tokenRingMLStatsStatus = createRequest
 
          a get tokenRingMLStatsStatus should now show underCreation
 
        - set tokenRingMLStatsStatus = valid
 
        Data collection will now be started on the
        tokenRingMLStatsTable
 
   - The Token Ring Ring Station Group
   - The Token Ring Ring Station Order Group
   - The Token Ring Ring Station Config Group
 
     To invalidate the tables:
 
        - set ringStationControlStatus = invalid
 
     To initiate data collection on the tables:
 
        - set ringStationControlStatus = createRequest
 
          a get ringStationControlStatus should now show underCreation
 
        - set ringStationControlStatus = valid
 
        Data collection will now be started on the
        ringStationControlTable, ringStationTable, ringStationOrderTable,
        and ringStationConfigControlTable.
 
 
     To generate entries in the ringStationConfigTable you
     need to:                                                                      
        - set ringStationConfigControlUpdateStats = updating
                                                                                   
          for the appropriate mac address. This variable is in the
          ringStationConfigControlTable.
   
                                                                                
 
   Below is an excerpt from rfc1271 - Remote Network Monitoring Management Information Base
   which describes in general the use of an EntryStatus variable to control the
   creation and invalidation of RMON tables.
 
   "           EntryStatus ::= INTEGER
                          { valid(1),
                            createRequest(2),
                            underCreation(3),
                            invalid(4)
                          }
 
               -- The status of a table entry.
               --
               -- Setting this object to the value invalid(4) has the
               -- effect of invalidating the corresponding entry.
               -- That is, it effectively disassociates the mapping
               -- identified with said entry.
               -- It is an implementation-specific matter as to whether
               -- the agent removes an invalidated entry from the table.
               -- Accordingly, management stations must be prepared to
               -- receive tabular information from agents that corresponds
               -- to entries currently not in use.  Proper
               -- interpretation of such entries requires examination
               -- of the relevant EntryStatus object.
               --
               -- An existing instance of this object cannot be set to
               -- createRequest(2).  This object may only be set to
               -- createRequest(2) when this instance is created.  When
               -- this object is created, the agent may wish to create
               -- supplemental object instances to complete a conceptual
               -- row in this table.  Immediately after completing the
               -- create operation, the agent must set this object to
               -- underCreation(3).
               --
               -- Entries shall exist in the underCreation(3) state until
               -- the management station is finished configuring the
               -- entry and sets this object to valid(1) or aborts,
               -- setting this object to invalid(4).  If the agent
               -- determines that an entry has been in the
               -- underCreation(3) state for an abnormally long time,
               -- it may decide that the management station has
               -- crashed.  If the agent makes this decision,
               -- it may set this object to invalid(4) to reclaim the
               -- entry.  A prudent agent will understand that the
               -- management station may need to wait for human input
               -- and will allow for that possibility in its
               -- determination of this abnormally long period."
 
    NOTE: If you are using a mib browser, you will have to make sure
          that the appropriate mibs are loaded:
            rfc1271 - Remote Network Monitoring Management Information Base and
            rfc1513 - Token Ring Extensions to the Remote Network Monitoring MIB:

          These are standard mibs and are therefore not supplied on your 8230
          diskette.
